Conversation
| "ibexa/shopping-list": "~5.0.x-dev", | ||
| "ibexa/phpstan": "~5.0.-dev", | ||
| "ibexa/connector-quable": "5.0.x-dev", | ||
| "ibexa/quable-client": "dev-reverted-open-api as 5.0.x-dev", |
There was a problem hiding this comment.
TODO: switched to stable branch after release
| hash = '#' + hash | ||
|
|
||
| if re.search("^https://[^@/]+.ibexa.co", path): | ||
| if re.search(r"^https?://", path): |
There was a problem hiding this comment.
Relaxed the rules to be able to query other pages - in this case, quable.com
docs/pim/customize_pim.md
Outdated
docs/pim/pim.md
Outdated
|
code_samples/ change report
|
| composer require ibexa/quable-client | ||
| composer require ibexa/connector-quable |
There was a problem hiding this comment.
Regarding API References, I thought we'll have to add them to DXP_ADD_ONS but, in fact, none of this two packages add something to the Contracts namespace or the REST ressources.
Am I right?
There was a problem hiding this comment.
You're right, but I'll add connector-quable to be future proof - ibexa/quable-client is considered internal
There was a problem hiding this comment.
In #3119 I added them both for the purpose of the test. I feel like they could be kept in case of a specific API is exposed in the future.
adriendupuis
left a comment
There was a problem hiding this comment.
month_change: true missing in several pages.
When moving from local to Quable:
- Can I use the local and the Quable PIM at the same time?
- How do I handle purchases without carts and orders?
- What happens to taxonomy tree(s) precisely?
- What are the product search criteria and sort clauses I'll have to stop using?
Some old pages could mention Quable
- Product catalog configuration could mention
quableas another possible value fortype. - Product search references could indicate what is supported by Quable.
| description: Quable PIM connector configuration reference for Ibexa DXP | ||
| page_type: reference |
There was a problem hiding this comment.
| description: Quable PIM connector configuration reference for Ibexa DXP | |
| page_type: reference | |
| description: Quable PIM connector configuration reference for Ibexa DXP | |
| page_type: reference | |
| month_change: true |
| @@ -0,0 +1,170 @@ | |||
| --- | |||
| description: Install and configure Quable PIM connector for Ibexa DXP | |||
There was a problem hiding this comment.
| description: Install and configure Quable PIM connector for Ibexa DXP | |
| description: Install and configure Quable PIM connector for Ibexa DXP | |
| month_change: true |
| description: Quable PIM integration with Ibexa DXP | ||
| page_type: landing_page |
There was a problem hiding this comment.
| description: Quable PIM integration with Ibexa DXP | |
| page_type: landing_page | |
| description: Quable PIM integration with Ibexa DXP | |
| page_type: landing_page | |
| month_change: true |
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | ||
| month_change: false |
There was a problem hiding this comment.
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | |
| month_change: false | |
| description: The Quable product guide describes how you can use the product data from Quable in Ibexa DXP to create marketing campaigns built around your products. | |
| month_change: true |
There was a problem hiding this comment.
There is probably more missing month_change: truethan those abvious ones.
|
|
||
| You can use [[= product_name =]] to manage product availability and pricing for [[= pim_product_name =]]'s products, including creating advanced pricing strategies with [discounts](discounts.md) combined with [regions](product_catalog_guide.md#regions) and [currencies](product_catalog_guide.md#currencies). | ||
|
|
||
| ## Known limitations |
There was a problem hiding this comment.
I feel like this isn't the place for this section as it get a bit too technical and detailed for a guide. But I see know better place.
As limitation to the capabilities, I would "hide" it a bit under this section.
| ## Known limitations | |
| ### Known limitations |
Or even move it down after Use cases?
| |[ProductName](productname_sort_clause.md)|Product's name| | ||
|
|
||
|
|
||
| ### Manage stock and pricing |
There was a problem hiding this comment.
| |[ProductName](productname_sort_clause.md)|Product's name| | |
| ### Manage stock and pricing | |
| |[ProductName](productname_sort_clause.md)|Product's name| | |
| ### Manage stock and pricing |
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | ||
| page_type: landing_page |
There was a problem hiding this comment.
This introduction to the total revamp of what was PIM (https://doc.ibexa.co/en/5.0/pim/pim/) worth being labeled as new.
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | |
| page_type: landing_page | |
| description: Ibexa DXP provides product catalog capabilities for managing products, product types, variants, attributes, pricing, and catalogs. | |
| page_type: landing_page | |
| month_change: true |
I like this new https://ez-systems-developer-documentation--3085.com.readthedocs.build/en/3085/product_catalog/product_catalog/ by the way.
|
|
||
| [[= product_name =]] offers robust product catalog infrastructure that can be used standalone. | ||
|
|
||
| You can also use [Quable Product Information Management (PIM)](quable/quable.md) that's fully integrated into the [[= product_name_base =]] ecosystem, or the [Remote PIM](add_remote_pim_support.md) to add integration with any external PIM system. |
There was a problem hiding this comment.
| You can also use [Quable Product Information Management (PIM)](quable/quable.md) that's fully integrated into the [[= product_name_base =]] ecosystem, or the [Remote PIM](add_remote_pim_support.md) to add integration with any external PIM system. | |
| You can also use [[[= pim_product_name =]] Product Information Management (PIM)](quable/quable.md) that's fully integrated into the [[= product_name_base =]] ecosystem, or the [Remote PIM](add_remote_pim_support.md) to add integration with any external PIM system. |
There was a problem hiding this comment.
This variable doesn't seem alway used. Did you create a vale rule for it?
| <li><a href="pim/catalogs/">Catalogs</a></li> | ||
| <li><a href="pim/prices/">Prices</a></li> | ||
| <li><a href="product_catalog/product_catalog_configuration/">Product catalog configuration</a></li> | ||
| <li><a href="product_catalog/quable_integration/">Quable PIM Integration</a></li> |
| product_name_cloud: 'Ibexa Cloud' | ||
| product_name_oss: 'Ibexa OSS' | ||
| product_name_engage: 'Ibexa Engage' | ||
| pim_product_name: 'Quable' |
There was a problem hiding this comment.
I'm not sure about this variable name regarding the existing ones about Ibexa.
But we could wait for other needs to rethink this.
| pim_product_name: 'Quable' | |
| pim_product_name: 'Quable PIM' | |
| pim_product_name_full: 'Quable Product Information Management' | |
| pim_product_name_base: 'Quable' |



Documentation for the upcoming Quable connector.
Most important changes:
ibexa_quable_instance_url